Password How To's

How to's for the Password guide.

How to Use It?

How to Use the Password Object

Once the Password object is added to a form, it allows users to enter data securely.
Since the characters are masked, it is especially preferred for fields such as password, secret codes, and private access keys.

Step-by-Step Usage

1. Add the Object to the Form

• Toolbox → Password → Drag and drop onto the form.

2. Configure General Properties

From the Property Viewer panel:

Property	Description
Name	The unique identifier of the object on the form.
Text	The visible label of the field on the form.
Visible	Sets whether the object is displayed on the form.
Enabled	Determines whether the user can enter data into the field.
Required	Defines whether the field must be filled out.

3. Use Events

The Password object supports specific events:

• On Value Changed → Triggered when the user changes the password value

---

What Is It Password?

What Is the Password Object?

The Password object is a special input field used when a form requires entering passwords, confidential information, or security-sensitive data.

When the user types into this field:

• The entered value is not displayed on the screen,
• Each character is shown as a dot (•) or the system’s masking character.

This ensures that confidential information cannot be read by third parties.

Where Is It Used?

• User login password fields
• PIN, private codes, or verification keys
• Sensitive information that should not be visible to everyone on the form
• Identity verification or security-related fields

How to Add It in the IDE?

1. While the form screen is active, open the Toolbox panel.
2. Locate the Password object in the list.
3. Drag and drop it onto the form.
4. When selected, the Property Viewer panel displays:
   • Appearance / Properties
   • Events

Notes

• The Password object behaves similarly to a TextBox but is visually masked.
• The entered value is processed as plain text when the form is saved; masking only applies to the user interface.

---

How to Use Client Enabled?

What is Client Enabled?

Client Enabled is a property that defines whether a form control is active (enabled) on the client side when the form is first loaded.
If it is set to True, the control is immediately usable by the user.
If it is set to False, the control is disabled and cannot be interacted with until a specific condition or rule activates it.

This property is especially useful for controlling the user’s interaction flow and applying dynamic behaviors using the Rule Manager.

What Does It Do?

The property allows developers to:

• Control when a form control becomes interactive.
• Prevent users from entering or changing data until prerequisites are met.
• Dynamically enable or disable controls based on user input or logic.

Example Scenario — Conditional Activation

Scenario:
A form contains a checkbox called “I Accept Terms” and a text field called “Signature.”
The goal is to make the “Signature” field inactive until the user checks “I Accept Terms.”

Steps to Implement:

1. Select the “Signature” field in the form editor.

2. In the Properties panel, find the Client Enabled field.

3. Set the value to False — the field will now be disabled by default when the form loads.

4. Open the Rule Manager.

5. Add a new rule:

   Condition:

Action:

6. Save and publish the form.

Result:

• When the form loads, the “Signature” field is disabled.
• Once the user checks “I Accept Terms,” the field automatically becomes active and editable.

Behavior Summary

Property State	Description
True	The control is active and ready for user interaction when the form loads.
False	The control is disabled at load time and can be enabled dynamically via rules or code.

Notes & Best Practices

• Use the Client Enabled property to manage client-side interactivity without requiring server actions.
• Combine it with Rule Manager to define when and how controls become active.
• Remember: if server enablement is disabled, the client cannot enable the control even if Client Enabled is set to True.
• By default, this property is set to True (active).

Summary

Client Enabled improves form usability by letting developers control when and how users interact with form controls.
It is essential for creating responsive, condition-based form experiences where user actions dynamically change the form’s state.

---

Purpose and Key Features

What Is the Purpose of the Password Object?

The Password object is designed to prevent entered data from being seen by others on the form.
It enhances user privacy and security, especially in fields where sensitive data is required.

In short:

It masks the entered value (•) and keeps it hidden.

Key Features

The following table lists the most commonly used and critical features of the Password object:

Feature	Description
Masking	Entered characters are automatically displayed as dots (•).
Required	Determines whether the password field must be filled in.
MaxLength / MinLength	Defines the minimum and maximum character length of the password.
Visible	Controls whether the field is visible on the form.
Enabled	Determines whether the user can interact with the field.
ReadOnly	Allows the field to be view-only (password cannot be edited).
On Value Changed Event	Triggered when the user changes the password value.

Where Is It Used?

• User login screens
• Authorization forms
• Transaction confirmation code screens
• PIN, token, or secret key input areas
• Membership, registration, or password reset forms

Why Use the Password Object?

Purpose	Explanation
Privacy	Prevents passwords from being seen by nearby users.
Security	Protects sensitive data from being openly displayed on forms.
User Experience	Provides a familiar and standard password input experience.

Conclusion

The Password object is one of the essential building blocks for secure data entry.
If your form requires protection of user privacy, it should always be used.